---
title: SAIF.Application.Claim overview
summary: High-level purpose, scope, and responsibilities for the claim-context application manager library.
status: draft
owner: SAIF Claims BOF team
last_reviewed: 2026-08-21
library: SAIF.Application.Claim
reference_type: embedded
---

# SAIF.Application.Claim overview

> **Documentation context:** Packaged Component (NuGet)

`SAIF.Application.Claim` is a Component-tier class library that provides claim/worker context management, per-claim security-flag evaluation, and transaction lifecycle orchestration for concrete claim-screen application managers* built on top of the externally-packaged BOF business-object layer.

## Purpose
- Provides an abstract application-manager base (`ClaimAppManager`) that concrete claim-screen application managers inherit from to orchestrate claim/worker context changes, security enforcement, and save (`Write`) transactions.
- Computes per-claim, per-user access flags (conflict, exposure, health-issue, hostile/secure) against the current user's AD-resource access token, and centralizes shared claim-domain message strings and the claim DPI connection key.
- Establishes the Oracle data portal for the claim domain and delegates all data reads/writes to externally-packaged business objects rather than issuing SQL directly.

## Responsibilities
- Own and mutate the current claim/worker context (`ClaimContext`) and re-derive claim data whenever that context changes.
- Enforce claim access restrictions via [BR-CLM-001](business-rules.md#br-clm-001-conflict-claim-access-restriction) through [BR-CLM-007](business-rules.md#br-clm-007-claim-not-found-messaging).
- Wrap subclass save logic in a transaction lifecycle with rollback-on-exception.
- Resolve the imaging API base URL via configuration to construct the claim-image API client.

## Key components
- `ClaimAppManager`: abstract centerpiece; claim context, security, and save/transaction orchestration.
- `ClaimContext`: immutable value object representing the current claim/worker context.
- `ClaimSecurity`: computes per-claim access flags for the current user.
- `ClaimUserAccess`: exposes named AD-resource checks via the inherited `HasAccess` lookup.
- `ClaimAppConstants`: shared message/constant strings and the claim DPI key.

## Related documentation
- [Index](index.md)
- [Architecture](architecture.md)
- [Dependencies](dependencies.md)
- [Operations and processes](operations-processes.md)
- [Business rules](business-rules.md)
- [Security and authorization](security-authorization.md)
- [Configuration](configuration.md)
- [API reference](api/index.md)

> **Note:** Statements marked with * were inferred from code structure, naming conventions, or
> contextual evidence where direct confirmation was not available in source artifacts. Statements
> marked with ** could not be confirmed; treat as unknown until verified.

## Sources
- `SAIF.Application.Claim\ClaimAppManager.vb`
- `SAIF.Application.Claim\ClaimContext.vb`
- `SAIF.Application.Claim\ClaimSecurity.vb`
- `SAIF.Application.Claim\ClaimUserAccess.vb`
- `SAIF.Application.Claim\ClaimAppConstants.vb`
- `SAIF.Application.Claim\SAIF.Application.Claim.vbproj`